Systems and methods for processing data messages from a user vehicle

ABSTRACT

A payment processor computing device for performing an electronic transaction initiated by a vehicle is described. The payment processor computing device is configured to receive a registration secure token from a vehicle computing device, the registration secure token corresponding to a cardholder and including an account identifier, a vehicle identifier, and a biometric identifier. The payment processor computing device is further configured to store the registration secure token in memory, receive an authorization request message associated with a payment transaction initiated by the cardholder using the vehicle computing device in communication with a merchant computing device wherein the authorization request message includes a transaction secure token, authenticate the authorization request message by matching the transaction secure token to the registration secure token, embed a matching indicator within the authorization request message, and transmit the authorization request message with the embedded matching indicator to an issuer.

BACKGROUND

This disclosure relates generally to systems and methods for dataprocessing in computer networks and, more particularly, to network-basedsystems and methods for processing data messages from a vehicle of auser.

Electronic transaction cards are widely used in the United States andelsewhere as a means to attach financial accounts to financialinstitutions and, in the case of credit cards, as a medium to createsmall loans and generate interest income for financial institutions. Auser of the transaction card, a cardholder, can initiate an electronictransaction to purchase goods and/or services from a merchant. Themerchant processes these transactions using a point-of-sale (POS) devicethat captures certain transaction information and communicates thisinformation over an interchange network to a merchant bank andultimately to an issuer. Information is then exchanged between theseparties over the interchange network until the transaction is completed.

Some vehicle models include electronic capabilities such as accessingthe Internet and accessing satellite navigation systems. Thesecapabilities can be available in vehicles through original equipmentmanufacturer (OEM) and/or aftermarket user interface devices integratedwithin the vehicle. Some of the interface devices merge hands-freetelephone service with access to Internet/satellite services. Typicalelectronic capabilities provide pre-set data to the vehicle such asdownloadable music. Other electronic capabilities provide directions toa particular location, for example, directions to a merchant's locationthat provides goods, such as a drive-through restaurant, and/orservices, such as a car wash. However, when the cardholder drives thesevehicles to the merchant, the cardholder still physically presents thetransaction card to the merchant to initiate the electronic transaction.Tasks such as paying for food at the drive-through require thecardholder to hand the transaction card to an employee of the merchant,the employee to process the transaction, and the employee to hand thetransaction card back to the cardholder. Sometimes, these time-consumingactivities are conducted in inclement weather such as rain, snow, orheat. Additionally, if the cardholder does not have the transaction cardin the vehicle (e.g., forgetting the transaction card at home), thecardholder is not able to initiate a transaction with the merchant andpurchase goods and/or services.

Accordingly, a system and method is needed that utilizes known protocolsfor communicating information between vehicle computing devices,merchant computing devices, and payment computing devices in order toenhance and further automate processing transactions and payments.

BRIEF DESCRIPTION

In one embodiment, a payment processor computing device for performingan electronic transaction initiated by a vehicle is provided. Thepayment processor computing device includes one or more processors incommunication with one or more memory devices. The payment processorcomputing device is configured to receive a registration secure tokenfrom a vehicle computing device, wherein the registration secure tokencorresponds to a cardholder and includes an account identifier, avehicle identifier, and a biometric identifier, and wherein thecardholder has an account associated with the account identifier for usein processing electronic transactions, the cardholder is associated witha vehicle having the vehicle identifier, and the cardholder isassociated with the biometric identifier. The payment processorcomputing device is further configured to store the registration securetoken in the one or more memory devices, receive an authorizationrequest message associated with a payment transaction initiated by thecardholder using the vehicle computing device in communication with amerchant computing device wherein the authorization request messageincludes a transaction secure token, authenticate the authorizationrequest message by matching the transaction secure token to theregistration secure token, embed a matching indicator within theauthorization request message, and transmit the authorization requestmessage with the embedded matching indicator to an issuer of the accountfor further processing.

In another aspect, a computer-implemented method for performing anelectronic transaction initiated by a vehicle using a payment processorcomputing device is provided. The computing device has at least oneprocessor and one or more memory devices. The method includes receiving,by the payment processor computing device, a registration secure tokenfrom a vehicle computing device, wherein the registration secure tokencorresponds to a cardholder and includes an account identifier, avehicle identifier, and a biometric identifier, and wherein thecardholder has an account associated with the account identifier for usein processing electronic transactions, the cardholder is associated witha vehicle having the vehicle identifier, and the cardholder isassociated with the biometric identifier. The method further includesstoring by the payment processor computing device the registrationsecure token in the one or more memory devices, receiving by the paymentprocessor computing device an authorization request message associatedwith a payment transaction initiated by the cardholder using the vehiclecomputing device in communication with a merchant computing devicewherein the authorization request message includes a transaction securetoken, authenticating by the payment processor computing device theauthorization request message by matching the transaction secure tokento the registration secure token, embedding a matching indicator withinthe authorization request message, and transmitting the authorizationrequest message with the embedded matching indicator to an issuer of theaccount for further processing.

In a further aspect, a non-transitory computer readable medium thatincludes computer executable instructions for performing an electronictransaction initiated by a vehicle using a payment processor computingdevice in communication with a payment network is provided. Whenexecuted by the payment processor computing device, the computerexecutable instructions cause the payment processor computing device toreceive a registration secure token from a vehicle computing device,wherein the registration secure token corresponds to a cardholder andincludes an account identifier, a vehicle identifier, and a biometricidentifier, and wherein the cardholder has an account associated withthe account identifier for use in processing electronic transactions,the cardholder is associated with a vehicle having the vehicleidentifier, and the cardholder is associated with the biometricidentifier. Other computer executable instructions that cause thepayment processor computing device to store the registration securetoken in the one or more memory devices, receive an authorizationrequest message associated with a payment transaction initiated by thecardholder using the vehicle computing device in communication with amerchant computing device wherein the authorization request messageincludes a transaction secure token, authenticate the authorizationrequest message by matching the transaction secure token to theregistration secure token, embed a matching indicator within theauthorization request message, and transmit the authorization requestmessage with the embedded matching indicator to an issuer of the accountfor further processing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1-6 show exemplary embodiments of the methods and systemsdescribed herein.

FIG. 1 is a schematic diagram illustrating a multi-party payment systemfor processing payment transactions using a payment card or paymentaccount in accordance with one embodiment of the present disclosure.

FIG. 2 is a block diagram of an exemplary embodiment of a paymentprocessing system including a vehicle computing device for initiatingpayment transactions in accordance with one embodiment of the presentdisclosure.

FIG. 3 is an example configuration of a user computing device operatedby a user for use in the payment processing system shown in FIG. 2.

FIG. 4 is an example configuration of a server computing device for usein the payment processing system shown in FIG. 2.

FIG. 5 is a block diagram of a payment processing system showing dataflow between various computing devices in accordance with one embodimentof the present disclosure.

FIG. 6 is a flowchart illustrating an exemplary method for using avehicle computing device when performing a transaction in accordancewith one embodiment of the present disclosure.

DETAILED DESCRIPTION

The methods and systems described herein relate to data processing in acomputer network, and more specifically, to processing data messagesfrom a vehicle of a user. The systems and methods further relate to anelectronic transaction payment card processing system, such as a paymentcard processing system using the MasterCard® interchange network(MasterCard is a registered trademark of MasterCard InternationalIncorporated located in Purchase, N.Y.). The MasterCard® interchangenetwork is a proprietary communications standard promulgated byMasterCard International Incorporated® for the exchange of electronictransaction data between financial institutions that have registeredwith MasterCard International Incorporated®.

The following detailed description illustrates embodiments of thedisclosure by way of example and not by way of limitation. It iscontemplated that the disclosure has general application to processingelectronic transaction data initiated by a vehicle computing device. Asused herein, an element or step recited in the singular and proceededwith the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “one embodiment” and/or “another embodiment”of the present invention are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

The embodiments described herein are directed to systems and methods forperforming a “cardless” transaction using a vehicle computing devicethrough use of a biometric identifier. The transaction is performed by auser of a payment card, referred to herein as a cardholder. A cardholderis issued a payment card by an issuer or an issuing bank. The cardholderis able to use the payment card at participating merchants to initiatetransactions. The merchant processes these transactions using apoint-of-sale (POS) device (or via a merchant website) that capturescertain transaction information and communicates this information overan interchange network (e.g., payment network) to a merchant bank andultimately to the issuer. Information is then exchanged between theseparties over the interchange network until the transaction is completed.

In the example embodiment, before the cardholder initiates a cardlesstransaction with a merchant, the cardholder may set up or register avehicle computing device to perform cardless electronic transactions.The transaction is cardless in that the cardholder does not have tophysically handle the payment card during a payment transaction. Forexample, the cardholder receives the payment card from an issuer, andenters registration information into the vehicle computing device toregister with a payment processing system that enables the vehiclecomputing device to electronically initiate cardless paymenttransactions. Registration information includes, without limitation,payment card information, contact information (e.g., an email addressand/or a telephone number), a promotion code, billing information,and/or shipping information. Payment card information may include, forexample, a payment card or payment account identifier (e.g., a primaryaccount number (PAN), a partial account number, and/or a card name), asecurity code, and/or an expiry date. Shipping information may include,for example, a delivery address and/or delivery instructions. In oneembodiment, the cardholder enters, among other data inputs, a PAN intothe vehicle computing device, and the PAN is stored in vehicle memory(e.g., memory of the vehicle computing device). In another embodiment,the PAN is entered into the vehicle computing device, but is then senton to a payment processor computing device where it is tokenized, andthe token PAN is returned to the vehicle computing device for storage.

Additionally, the cardholder may provide a biometric sample that is tobe associated with the other registration information provided that isstored in the vehicle computing device. Biometric samples include,without limitation, a fingerprint image, a voice recording, a retinalimage, facial recognition, palm print image, iris recognition, and thelike. The biometric sample is unique to the cardholder and difficult toduplicate and/or forge by an unauthorized user. The biometric sample isstored and associated with a biometric identifier. Additionally, thebiometric identifier is associated with the stored registrationinformation and facilitates secure authorization of transactionsinitiated using any of the registration information. A biometric inputdevice in communication with the vehicle computing device may be usedfor the cardholder to enter the biometric sample. For example, afingerprint or palm reader/scanner may be located on a steering wheel oron an interactive touch screen, a retinal or iris reader/scanner may belocated on a rearview mirror or on a dashboard, and voicereader/recorder may be coupled to an audio system in the vehicle. Insome embodiments, the biometric input device is proximate to a driver'sseat within the vehicle. In other embodiments, the biometric inputdevice is integral to a cardholder's user computing device (e.g., smartphone, tablet, laptop computer), such that the biometric sample may beuploaded to the vehicle computing device from the cardholder's usercomputing device.

Moreover, the cardholder may enter vehicle information and/or identifierthat corresponds to the vehicle. Vehicle information includes, withoutlimitation, a vehicle identification number (VIN) or any other uniqueidentifier. The vehicle information may be preloaded on the vehiclecomputing device or may be input by the cardholder. The registrationprocess may further include setting up one or more additional vehicleinformation systems to provide information during a transaction, such asa vehicle navigation or GPS system (e.g., to provide navigational orlocation information), a vehicle maintenance system or odometer (e.g.,to provide mileage information), a vehicle wireless network (e.g., toprovide information regarding connected mobile computing devices, suchas a cardholder's smart phone within the vehicle), and/or additionalvehicle information systems.

In the example embodiment, the payment account identifier, the biometricidentifier, and the vehicle identifier provided during the registrationphase are used to create a secure token that is unique to thecombination of the cardholder and the vehicle. This secure token isreferred to herein as a “registration secure token.” The registrationsecure token is stored at a memory associated with the paymentprocessing system (e.g., in a database accessible to a paymentprocessor) and is used for authentication of payment transactionsinitiated by the vehicle computing device. The registration secure tokenis also stored at the vehicle computing device, and is transmitted toand stored in a computing device associated with the issuer. In someembodiments, the vehicle computing device stores registration securetokens corresponding to more than one cardholder account. For example, avehicle owner may have more than one cardholder account, or more thanone cardholder may drive the vehicle, such as more than one member of afamily.

To use the vehicle computing device to initiate a cardless paymenttransaction, the cardholder drives and/or directs the vehicle to amerchant location. For example, a merchant may provide drive-up orcurb-side products and/or services, such as a car wash, a drive-through,and the like. To pay for the merchant's products and/or services, thecardholder connects the vehicle computing device to the merchant's POSdevice (e.g., directly, such as over a wireless communication link, orover a payment network), and initiates the transaction with the merchantvia the vehicle computing device. To initiate the transaction, thecardholder inputs a biometric sample using a biometric input device. Thebiometric sample is compared to the stored biometric sample and, if theinput biometric sample matches the stored biometric sample, the vehiclecomputing device generates a secure token associated with the paymenttransaction, referred to herein as a “transaction secure token.” Thetransaction secure token includes the account identifier and vehicleidentifier stored at the vehicle computing device. The transactionsecure token also includes at least one of the biometric identifierassociated with the stored biometric sample and a copy of the inputbiometric sample. The vehicle computing device provides the transactionsecure token to the merchant POS device.

The merchant POS device (and/or another merchant computing device)generates a payment authorization request message (e.g., an ISO 8583computer message) that includes the transaction secure token, andtransmits the payment authorization request message to the paymentprocessing network for further processing.

Upon receipt of the payment authorization request message, a paymentprocessor computing device associated with the payment processingnetwork authenticates the payment authorization request message. Morespecifically, the payment processor computing device compares thetransaction secure token with the stored registration secure token. Upondetermining that the transaction secure token included in the paymentauthorization request message matches the stored registration securetoken, the payment processor computing device embeds a matchingindicator into the authorization request message. The matching indicatoradvises the issuer that the received transaction secure token matchesthe stored registration secure token, and thus, the payment processorcomputing device has initially verified the payment transaction as beinginitiated by an authorized cardholder. The matching indicator acts as aflag to the issuer that initial verification of the payment transactionhas been performed. In the example embodiment, the issuer may forego oneor more additional verification processes and/or may otherwise expediteauthorization. In other words, the matching indicator embedded by thepayment processor computing device facilitates reducing needlessdeclines, thereby improving network efficiency and network bandwidth,and facilitates improving authorization efficiency by enabling expeditedissuer authorization of transactions.

The payment processor computing device transmits the authorizationrequest message with the embedded matching indicator to the issuer forfurther authorization processing (e.g., authorization or decline). Theissuer determines whether the cardholder has sufficient funds to coverthe transaction, and may further perform one or more additionalauthentication and/or verification processes. In some embodiments, upondetection of the embedded matching indicator, the issuer expedites theauthentication and/or verification process. If the issuer approves thetransaction, the issuer transmits an authorization response messagethrough the payment processing network to the merchant POS device.

However, if the transaction secure token included within the paymentauthorization request message does not match the stored registrationsecure token, then the payment processor computing device transmits theauthorization request message on to the issuer with a “no-match”indicator embedded therein. The no-match indicator advises the issuerthat the received transaction secure token does not match the storedregistration secure token, and thus, the payment processor computingdevice has not verified the payment transaction as being initiated by anauthorized cardholder. The issuer may then determine whether to declinethe transaction for not being a verified cardholder transaction, or toapprove the transaction anyway. Additionally or alternatively, theissuer may use the matching indicator or the no-match indicator embeddedin received authorization request messages to update internalfraud-related processes associated with the vehicle and/or thecardholder. For example, if a no-match indicator is received in anauthorization request message associated with a particular vehicle, theissuer may initiate additional authentication processes for apredetermined number of subsequent payment transactions initiated usingthat vehicle. As another example, if a particular cardholder initiates aplurality of payment transactions (e.g., a predetermined number oftransactions, e.g., 10 transactions) with a particular merchant, each ofwhich is associated with an authorization request message including amatching indicator, the issuer may expedite and/or forego one or moreissuer verification/authentication processes for a subsequent paymenttransaction initiated by the cardholder at that merchant.

In some embodiments, if the transaction secure token does not match theregistration secure token, then the payment processor computing devicewill automatically generate and transmit an authorization responsemessage back to the merchant that declines the transaction on behalf ofthe issuer. The decline message includes the “no-match” indicatorembedded in the authorization response message. The payment processorcomputing device may further transmit a notification message to theissuer, notifying the issuer of the declined payment transaction basedupon the lack of match between the transaction secure token and theregistration secure token.

In some embodiments, the payment processor computing device furtherverifies the payment authorization request message by applying at leastone verification rule and determining that the payment authorizationrequest message is a verified message. For example, in one embodiment,the vehicle computing device retrieves a current location of the vehicle(at the time the payment transaction is initiated) from a vehicle GPSdevice (or other location system of the vehicle) and transmits thecurrent location of the vehicle to the merchant POS device along withthe transaction secure code. The merchant POS device embeds the locationof the vehicle into the payment authorization request message. Thepayment processor computing device compares the location of the vehiclewith a location of the merchant (determined, for example, using alook-up table that associates a merchant identifier with a merchantlocation). The payment authorization request message is verified if itis determined that the current location of the cardholder's vehiclecorresponds to the location of the merchant that sent the paymentauthorization request message. However, if the vehicle location and themerchant location do not correspond, the payment authorization requestmessage is rejected or declined. In another example, the vehiclecomputing device retrieves a current mileage of the vehicle (at the timethe payment transaction is initiated) from an odometer of the vehicleand transmits the current mileage to the merchant POS device along withthe transaction secure code. The merchant POS device embeds the mileageof the vehicle into the payment authorization request message. Thepayment processor computing device compares the current mileage of thevehicle with a previous mileage of the vehicle (determined, for example,using a look-up table that stores vehicle mileage received duringprevious authorized payment transactions). The payment authorizationrequest message is verified if it is determined that the current mileageof the cardholder's vehicle is greater than a previous mileage of thevehicle corresponding to a previous transaction. However, if the currentmileage of the vehicle is less than a previous transaction's mileagethen the payment authorization request is rejected or declined.

In yet another example, the cardholder registers one or more usercomputing devices (e.g., a smart phone) with the payment processingsystem, such that the user computing device is associated with thecardholder. For instance, the cardholder may provide an identifier ofthe user computing device that is subsequently verified by the paymentprocessing system, such as a phone number or other unique identifier.When a payment transaction is initiated using the vehicle computingdevice, the vehicle computing device may further transmit the identifierof any user computing devices that are connected to a wireless networkof the vehicle (e.g., a Bluetooth® network or a mobile “hot-spot”) tothe merchant POS. The merchant POS embeds the user computing deviceidentifier into the payment authorization request message. The paymentprocessor computing device compares the user computing device identifierwith any stored user computing device identifier(s) registered by thecardholder with the payment processing system. The payment authorizationrequest message is verified if it is determined that the user computingdevice identifier in the payment authorization request message matches astored user computing device identifier. If no user computing deviceidentifier is embedded in the payment authorization request messageand/or if non-stored user computing device identifier(s) are embedded,the payment authorization request message may not be declined, butadditional authentication and/or verification processes may beinitiated.

In other embodiments, the payment processor computing device receivescoupons from a merchant. The payment processor computing deviceidentifies one or more cardholders and/or corresponding vehicles thathave a prior transaction history with the merchant and distributes thecoupons to the vehicle computing device, to be used in a futuretransaction with the merchant. As such, the payment processor computingdevice facilitates transmitting merchant coupons to the cardholder andthe vehicle computing device for use in future merchant transactions.

The methods and systems described herein may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof,wherein the technical effect is achieved by performing at least one of:(a) registering by a cardholder with the payment processor computingdevice, which may include downloading an app (e.g., computer applicationthat includes computer-implemented instructions) that enables thecardholder's vehicle computing device to communicate with a merchantcomputing device (e.g., POS device); (b) inputting payment informationinto the vehicle computing device or a client computing device toregister the vehicle for initiating payment transactions, the paymentinformation includes, without limitation, payment card information,contact information (e.g., an email address and/or a telephone number),a promotion code, billing information, and/or shipping information,wherein the payment card information may include, for example, a cardidentifier (e.g., a primary account number (PAN), a partial accountnumber, and/or a card name), a security code, and/or an expiry date, andwherein the PAN or a tokenized PAN is stored in the vehicle memory; (c)inputting an input biometric sample of the cardholder for storing in thevehicle computing device or at the payment processor computing device,the biometric information including, without limitation, a fingerprintimage, a voice recording, a retinal image, facial recognition, palmprint image, iris recognition, and the like; (d) positioning the vehiclehaving the vehicle computing device in close proximity to the merchant'slocation (e.g., the merchant may provide drive up or curb side productsand/or services); (e) initiating the transaction by inputting abiometric input of the transaction initiator into the vehicle computingdevice; (f) comparing the biometric input to the biometric sample storedin the system to verify the initiator of the transaction as the actualcardholder; (g) if the biometric input matches the biometric samplestored in the system, then the vehicle computing device generates asecure token for the transaction and transmits it to the merchantcomputing device (e.g., POS device), wherein the secure token is uniqueto the cardholder and includes an account identifier, a vehicleidentifier, and a biometric identifier; (h) generating, by the merchantcomputing device, a payment authorization request message (e.g., ISO8583 computer message) for the transaction that includes the securetoken, transmitted from the cardholder via the vehicle computing device,and the transaction data for the transaction; (i) upon receipt of thepayment authorization request message, the payment processor computingdevice authenticates the payment authorization request message bydetermining that the secure token sent with the payment authorizationrequest message matches a stored secure token corresponding to thecardholder that was created as part of the registration; (j) if thesecure token from the payment authorization request message matches thestored secure token at the payment processor computing device,embedding, by the payment processor computing device, a matchingindicator into the authorization message (e.g., ISO 8583 message)advising the issuer that the received secure token matches the storedsecure token, and thus, the transaction has been initially verified asbeing initiated by the authorized cardholder; (k) if, however, thesecure token included within the payment authorization request messagedoes not match the stored secure token at the payment processorcomputing device, either (1) embedding, by the payment processorcomputing device, a “no match” indicator into the authorization requestmessage so that the issuer can decline the transaction for not being averified cardholder transaction, or (2) automatically declining, by thepayment processor computing device, the transaction on behalf of theissuer; and (l) transmitting, from the payment processor computingdevice to the merchant, an authorization response message authorizingthe transaction if the received secure token matches the stored securetoken.

The systems and methods described herein provide the technicaladvantages of at least one of: (a) enabling communication between amerchant computing device and a vehicle computing device forfacilitating an electronic transaction; (b) enabling electronictransactions initiated by a user using a vehicle computing device; (c)initiating a payment transaction using a vehicle computing device byinputting a biometric input that is compared to a stored biometricsample for authenticating the user as the authentic cardholder; (d)enabling biometric authentication of a cardholder to initiate a paymenttransaction from a vehicle computing device without the cardholderhaving to leave the vehicle; (e) verifying electronic transactions viadata supplied by the user's vehicle; (f) creating, as part of theregistration process, a registration secure token at the vehiclecomputing device that is unique to the cardholder and includes anaccount identifier, a biometric identifier, and a vehicle identifier,wherein the registration secure token is stored at the payment processorcomputing device, and wherein each time a payment transaction isinitiated by the cardholder using the vehicle computing device atransaction secure token is generated by the vehicle computing device sothat it can be matched to the stored (registration) secure token toconfirm that the authentic cardholder is the one initiating thetransaction; (g) expediting issuer authentication/verificationprocessing by embedding a matching indicator in an authorization requestmessage that indicates initial verification has already been performed,thereby decreasing network latency; (h) improving network efficiency andbandwidth by reducing needless issuer declines using matching indicatorsto improve issuer fraud processing; and/or (i) improving issuer fraudprocesses using matching/no-match indicators to identify low- orhigh-risk cardholders and/or vehicles.

In one embodiment, a computer program is provided, and the program isembodied on a computer-readable medium. In an example embodiment, thesystem is executed on a single computer system, without requiring aconnection to a server computer. In a further example embodiment, thesystem is being run in a Windows® environment (Windows is a registeredtrademark of Microsoft Corporation, Redmond, Wash.). In yet anotherembodiment, the system is run on a mainframe environment and a UNIX®server environment (UNIX is a registered trademark of X/Open CompanyLimited located in Reading, Berkshire, United Kingdom). In a furtherembodiment, the system is run on an iOS® environment (iOS is aregistered trademark of Cisco Systems, Inc. located in San Jose,Calif.). In yet a further embodiment, the system is run on a Mac OS®environment (Mac OS is a registered trademark of Apple Inc. located inCupertino, Calif.). The application is flexible and designed to run invarious different environments without compromising any majorfunctionality. In some embodiments, the system includes multiplecomponents distributed among a plurality of computing devices. One ormore components are in the form of computer-executable instructionsembodied in a computer-readable medium. The systems and processes arenot limited to the specific embodiments described herein. In addition,components of each system and each process can be practicedindependently and separately from other components and processesdescribed herein. Each component and process can also be used incombination with other assembly packages and processes.

The systems and processes described herein are not limited to thespecific embodiments described herein. In addition, components of eachsystem and each process can be practiced independent of and separatefrom other components and processes described herein. Each component andprocess also can be used in combination with other assembly packages andprocesses.

The following detailed description illustrates embodiments of thedisclosure by way of example and not by way of limitation. It iscontemplated that the disclosure has general application to processingelectronic transaction data initiated by a vehicle computing device inindustrial, commercial, and residential applications.

FIG. 1 is a schematic diagram illustrating a multi-party payment cardprocessing system 20 for processing payment card transactions inaccordance with one exemplary embodiment of the disclosure. In theexemplary embodiment, the payment card system 20 relates to a system,such as a payment card system using the MasterCard® payment system. TheMasterCard® payment system is a proprietary communications standardpromulgated by MasterCard International Incorporated® for the exchangeof financial transaction data between financial institutions that aremembers of MasterCard International Incorporated®.

In the example payment card system 20, a financial institution such asan issuer 30 issues a payment card, such as a credit card account or adebit card account, to a cardholder 22, who uses the payment card totender payment for a purchase from a merchant 24. More particularly,cardholder 22 enters payment card information, along with additionalregistration information, into a vehicle computing device of a vehicle50. Where reference is made to vehicle 50 performing one or moreactions, it should be understood that the vehicle computing device 102(shown in FIG. 2) may perform such actions. Vehicle 50 generates andtransmits a registration secure token, which includes an accountidentifier (which may itself be tokenized), a vehicle identifier (e.g.,a VIN), and a biometric identifier (associated with a biometric sampleprovided by cardholder 22 during registration). Vehicle 50 transmits theregistration secure token to a payment processor computing device (notshown in FIG. 1) associated with a payment processing network 28, wherethe registration secure token is stored. During a purchase transaction,cardholder 22 inputs a biometric sample to vehicle 50, which is comparedwith a stored biometric sample. If the biometric samples match, vehicle50 transmits a transaction secure token including the biometricidentifier, the account identifier, and the vehicle identifier tomerchant 24.

To accept payment with the payment card, merchant 24 must normallyestablish an account with a financial institution that is part of thefinancial payment system. This financial institution is usually calledthe “merchant bank” or the “acquiring bank” or “acquirer.” In theexample embodiment, when cardholder 22 tenders payment for a purchasewith a payment card, merchant 24 requests authorization from merchantbank 26 for the amount of the purchase. The request may be performedover the telephone, but is usually performed through the use of apoint-of-sale (POS) terminal 27 (or via a merchant website), which readsthe cardholder's account information from a magnetic stripe, a chip,embossed characters, and the like, included on the payment card andcommunicates electronically with the transaction processing computers ofmerchant bank 26. In the example embodiment, POS terminal 27communicates with vehicle 50 to receive the transaction secure token.POS terminal 27 generates an authorization request message including thetransaction secure token and transmits the authorization request messageto network 28. Alternatively, merchant bank 26 may authorize a thirdparty to perform transaction processing on its behalf. In this case, thepoint-of-sale terminal will be configured to communicate with the thirdparty. Such a third party is usually called a “merchant processor,” an“acquiring processor,” or a “third party processor.”

The payment processing computing device of network 28 performs aninitial authentication or verification of the payment transaction bycomparing the transaction secure token with the registration securetoken. If the tokens match, network 28 will embed a matching indicatorwithin the authorization request message and will transmit theauthorization request message to issuer bank 30, which determineswhether a cardholder's account 32 is in good standing and whether thepurchase is covered by the cardholder's available credit line or accountbalance. Based on these determinations as well as the matching indicator(or, alternatively, the receipt of an authorization request messageincluding an embedded no-match indicator), the request for authorizationwill be declined or accepted. If the request is accepted, anauthorization code may be issued to merchant 24.

When a request for authorization is accepted, the available credit lineor available balance of cardholder's account 32 is decreased. Normally,a charge is not posted immediately to a cardholder's account becausebankcard associations, such as MasterCard International Incorporated®,have promulgated rules that do not allow a merchant to charge, or“capture,” a transaction until goods are shipped or services aredelivered. When a merchant ships or delivers the goods or services,merchant 24 captures the transaction by, for example, appropriate dataentry procedures on the point-of-sale terminal. If a cardholder cancelsa transaction before it is captured, a “void” is generated. If acardholder returns goods after the transaction has been captured, a“credit” is generated. For debit card transactions, when a request for aPIN authorization is approved by the issuer, the cardholder's account 32is decreased. Normally, a charge is posted immediately to cardholder'saccount 32. The bankcard association then transmits the approval to theacquiring processor for distribution of goods/services, or informationor cash in the case of an ATM. After a transaction is captured, thetransaction is settled between merchant 24, merchant bank 26, and issuer30. Settlement refers to the transfer of financial data or funds betweenthe merchant's account, merchant bank 26, and issuer 30 related to thetransaction. Usually, transactions are captured and accumulated into a“batch,” which is settled as a group.

FIG. 2 is a block diagram of an exemplary payment processing system 100including a vehicle computing device 102 (which may be included invehicle 50, shown in FIG. 1) in accordance with one embodiment of thepresent disclosure. System 100 can be utilized by cardholders, forexample cardholder 22 shown in FIG. 1, as part of a process ofinitiating an electronic transaction to purchase goods and/or services(collectively an “item”) as described below. In addition, system 100 isa payment card account including vehicle computing device 102, which acardholder may use to connect to a merchant's point-of-service (POS)terminal 104, and/or conduct electronic transactions without thecardholder having to leave the vehicle.

More specifically, in the example embodiment, system 100 includes aserver system 106, which is a type of computing device, and a pluralityof sub-systems (also referred to as client systems 108) connected toserver system 106. In one embodiment, client systems 108 are computingdevices that includes a web browser and a memory device, such thatserver system 106 is accessible to client systems 108 using a network110. In one embodiment, server system 106 may be associated with thepayment processor and may be the payment processor computing device.Network 110 may include the Internet and/or one or more other networks.For example, client systems 108 are interconnected through a wirelessnetwork, a wired network, a telephone network, a cable network, acombination thereof, and the like. Examples of a wireless networkinclude networks such as WiFI, WiMAX, WiBro, local area network (LAN),personal area network (PAN), metropolitan area network, cellular,Bluetooth and the like. Client systems 108 may be any computing devicecapable of interconnecting to the Internet including a smart phone,laptop, desktop, tablet, wearable device (e.g., a “smart watch”), and/orany other computing device.

System 100 also includes POS terminals 104, which are connected toclient systems 108 through network 110 and may be connected to serversystem 106 through network 110. POS terminals 104 are interconnected tothe Internet through many interfaces including a network, such as alocal area network (LAN) or a wide area network (WAN),dial-in-connections, cable modems, wireless modems, and specialhigh-speed ISDN lines. POS terminals 104 may be any device capable ofinterconnecting to the Internet and including an input device capable ofreading information from a cardholder's payment card and/or from vehiclecomputing device 102. POS terminal 104 may also include a websiteassociated with a merchant that is hosted by a computing device fordisplay on the vehicle computing device 102 or on one of client devices108.

A database server 112 is connected to a database 114, which containsinformation on a variety of matters, as described below in greaterdetail. In one embodiment, centralized database 114 is stored on serversystem 106 and can be accessed by cardholders at one of client systems108 by logging onto server system 106 through one of client systems 108.In an alternative embodiment, database 114 is stored remotely fromserver system 106 and may be non-centralized. Database 114 may storetransaction data generated as part of sales activities conducted overthe bankcard network including data relating to merchants, accountholders or customers, and purchases. Database 114 may also store accountdata including at least one of a cardholder name, a cardholder address,an account number, and other account identifiers. Database 114 may alsostore merchant data including a merchant identifier that identifies eachmerchant registered to use the payment account card network, andinstructions for settling transactions including merchant bank accountinformation. Database 114 may also store PAN numbers (or tokenizedversions of the PANs) or bank account numbers for various partiesincluding merchants and customers, along with payment accountidentifiers such as secure tokens, biometric identifiers, and other datanecessary to implement the system and processes described herein.

System 100 also includes vehicle computing device 102, which isconfigured to communicate with at least one of POS terminal 104, clientsystems 108, and server system 106. In one embodiment, vehicle computingdevice 102 is associated with or controlled by a cardholder making apurchase using a payment card account and payment processing system 100.In the exemplary embodiment, vehicle computing device 102 is a componentof a vehicle (e.g., vehicle 50) such as an on-board computing device. Inother embodiments, vehicle computing device 102 is a computing devicecommunicatively coupled to a vehicle such as a smart phone, laptop,desktop, tablet, wearable device, and/or any other computing devicecapable of interconnecting to the Internet. Vehicle computing device 102is interconnected to the Internet through many interfaces including anetwork, such as a LAN or a WAN, dial-in-connections, cable modems,wireless modems, and special high-speed ISDN lines. Vehicle computingdevice 102 is configured to communicate with POS terminal 104 usingvarious outputs including, for example, Bluetooth communication, radiofrequency communication, near field communication, network-basedcommunication, and the like.

In the example embodiment, one of client systems 108 may be associatedwith an acquirer, a cardholder, or a customer; while another one ofclient systems 108 may be associated with an issuer; POS terminal 104may be associated with a merchant; vehicle computing device 102 may beassociated with a cardholder or a customer; and server system 106 may beassociated with a payment network or an interchange network (e.g.,network 28, shown in FIG. 1).

In the example embodiment, server system 106 may be associated with apayment network, and may be referred to as a payment processor computingdevice. Server system 106 may be used for processing transaction data.In addition, at least one of client systems 108 may include a computersystem associated with an issuer of a transaction card. Accordingly,server system 106 and client systems 108 may be utilized to processtransaction data relating to purchases made by a cardholder utilizing atransaction card that is processed by the payment network and issued bythe associated issuer. Another client system 108 may be associated witha user or a cardholder seeking to register access information or processa transaction with at least one of the payment network, the issuer, thePOS terminal 104, or the merchant computer.

The embodiments illustrated and described herein as well as embodimentsnot specifically described herein but within the scope of aspects of theinvention constitute exemplary means for performing an electronictransaction, and more particularly, constitute exemplary means forperforming an electronic transaction using vehicle computing device 102.For example, server system 106, POS terminal 104, client system 108,vehicle computing device 102, or any other similar computing device,programmed with computer-executable instructions to execute processesand techniques with a processor as described herein, constitutesexemplary means for enabling a cardholder to execute an electronictransaction with a merchant.

FIG. 3 is an example configuration of a user computing device 200operated by a user 201 for use in the payment processing system 100(shown in FIG. 2). User computing device 200 may include, but is notlimited to, client systems 108, point-of-service (POS) terminal 104, andvehicle computing device 102 (all shown in FIG. 2).

User computing device 200 includes a processor 205 for executinginstructions. In some embodiments, executable instructions are stored ina memory area 210. Processor 205 may include one or more processingunits (e.g., in a multi-core configuration) for executing instructions.Memory area 210 is any device allowing information such as executableinstructions and/or other data to be stored and retrieved. Memory area210 may include one or more computer readable media.

User computing device 200 also includes at least one media outputcomponent 215 for presenting information to user 201. Media outputcomponent 215 is any component capable of conveying information to user201. For example, media output component 215 includes an output adaptersuch as a video adapter and/or an audio adapter. The output adapter isoperatively coupled to processor 205 and operatively couplable to anoutput device such as a display device (e.g., a liquid crystal display(LCD), organic light emitting diode (OLED) display, cathode ray tube(CRT), or “electronic ink” display) or an audio output device (e.g., aspeaker or headphones). Stored in memory area 210 are, for example,computer readable instructions for providing a user interface to user201 via media output component 215.

Additionally, user computing device 200 includes an input device 220 forreceiving input from user 201. For example, user 201 may use inputdevice 220 to enter account identifiers, vehicle identifiers, and/orbiometric identifiers. Input device 220 may include, for example, akeyboard, a pointing device, a mouse, a stylus, a touch sensitive panel(e.g., a touch pad or a touch screen), a gyroscope, an accelerometer, aposition detector, an audio input device, a fingerprint reader/scanner,a palm print reader/scanner, a iris reader/scanner, a retinareader/scanner, a profile scanner, and the like. A single component,such as a touch screen, may function as both an output device of mediaoutput component 215 and input device 220. In other embodiments, inputdevice 220 may be commutatively coupled to user computing device 200 andlocated at a remote position. For example, vehicle computing device 102may be coupled to input device 220 that includes a fingerprintreader/scanner positioned on a steering wheel. In another example,vehicle computing device 102 may be coupled to input device 220 thatincludes a retina reader/scanner positioned on a rear view mirror.

User computing device 200 may also include a communication interface225, which is communicatively couplable to a remote device such asserver system 106 (shown in FIG. 2) and/or POS terminal 104.Communication interface 225 may include, for example, a wired orwireless network adapter or a wireless data transceiver for use with amobile phone network (e.g., Global System for Mobile communications(GSM), 3G, 4G or Bluetooth) or other mobile data network (e.g.,Worldwide Interoperability for Microwave Access (WIMAX)).

Stored in memory area 210 are, for example, computer readableinstructions for providing a user interface to user 201 via media outputcomponent 215 and, optionally, receiving and processing input from inputdevice 220. A user interface may include, among other possibilities, aweb browser and client application. Web browsers enable cardholders,such as user 201, to display and interact with media and otherinformation typically embedded on a web page or a website from serversystem 106. A client application allows user 201 to interact with aserver application from server system 106.

In general during a transaction, the cardholder as user 201 drivesand/or directs a vehicle including user computing device 200, such asvehicle computing device 102, to the merchant's location. To purchasethe merchant's products and/or services, user 201 connects (e.g.,directly or over the payment network) vehicle computing device 102 tothe merchant's user computing device 200, such as through POS terminal104, and initiates the electronic transaction. To initiate thetransaction, user 201 inputs via input device 220 a biometric sample atthe beginning of the transaction. Vehicle computing device 102 generatesa transaction secure token including a biometric identifier of thebiometric sample and/or the biometric sample itself and transmits thetransaction secure token to POS terminal 104 from vehicle computingdevice 102.

More specifically, user 201 initiates the transaction by inputting abiometric input into vehicle computing device 102; vehicle computingdevice 102 compares the biometric input to a stored biometric sample toverify user 201 (and the initiator of the transaction) as the actualcardholder 22; if the biometric input matches the stored biometricsample, then vehicle computing device 102 generates a transaction securetoken for the transaction and transmits it to POS terminal 104; POSterminal 104 then generates a payment authorization request message forthe transaction that includes the transaction secure token along withother transaction data for sending to payment processor computing device106 (shown in FIG. 2) for further processing described below.

FIG. 4 is an example configuration of a server computing device 275,such as server system 106 and/or database server 112, for use in paymentprocessing system 100 (all shown in FIG. 2). Server computing device 275includes a processor 280 for executing instructions. Instructions may bestored in a memory area 285, for example. Processor 280 may include oneor more processing units (e.g., in a multi-core configuration) forexecuting instructions. The instructions may be executed within avariety of different operating systems on server computing device 275,such as UNIX, LINUX, Microsoft Windows®, etc. It should also beappreciated that upon initiation of a computer-based method, variousinstructions may be executed during initialization. Some operations maybe required in order to perform one or more processes described herein,while other operations may be more general and/or specific to aparticular programming language (e.g., C, C#, C++, Java, or othersuitable programming languages).

Processor 280 is operatively coupled to a communication interface 290such that server computing device 275 is capable of communicating with aremote device such as user computing device 200 (shown in FIG. 3) oranother server computing device 275. For example, communicationinterface 290 may receive requests from client systems 108,point-of-service (POS) terminal 104, and/or vehicle computing device 102via the Internet, as illustrated in FIG. 2. Communication interface 290may include, for example, a transceiver, a transmitter, a receiver, andEthernet communication interface, an RS-485/EIA-485 communicationinterface, a GPM communications interface, a programmable logiccontroller, an RS-322 communication interface, and/or any othercommunication interface device and/or component.

Processor 280 may also be operatively coupled to a storage device 270.Storage device 270 is any computer-operated hardware suitable forstoring and/or retrieving data. In some embodiments, storage device 270is integrated in server computing device 275. For example, servercomputing device 275 may include one or more hard disk drives as storagedevice 270. In other embodiments, storage device 270 is external toserver computing device 275 and may be accessed by a plurality of servercomputing devices 275. For example, storage device 270 may includemultiple storage units such as hard disks or solid state disks in aredundant array of inexpensive disks (RAID) configuration. Storagedevice 270 may include a storage area network (SAN) and/or a networkattached storage (NAS) system.

In some embodiments, processor 280 is operatively coupled to storagedevice 270 via a storage interface 295. Storage interface 295 is anycomponent capable of providing processor 280 with access to storagedevice 270. Storage interface 295 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 280with access to storage device 270.

Memory area 285 may include, but is not limited to, random access memory(RAM) such as dynamic RAM (DRAM) or static RAM (SRAM), read-only memory(ROM), erasable programmable read-only memory (EPROM), electricallyerasable programmable read-only memory (EEPROM), and non-volatile RAM(NVRAM). The above memory types are exemplary only, and are thus notlimiting as to the types of memory usable for storage of a computerprogram.

In general, upon receipt of a payment authorization request message fromthe merchant, server computing device 275 (e.g., payment processorcomputing device 106) authenticates the payment authorization requestmessage. More specifically, the server computing device 275 determinesthat a transaction secure token sent with the payment authorizationrequest message matches a stored registration secure token correspondingto the cardholder that was created as part of a registration process.

If the transaction secure token matches the registration secure token,then server computing device 275 embeds a matching indicator into theauthorization request message, the matching indicator advising theissuer that the transaction secure token matches the registration securetoken, and thus, the transaction has been initially verified as beinginitiated by the authorized cardholder. If, however, the transactionsecure token does not match the registration secure token, then servercomputing device 275 may either (i) embed a “no match” indicator withinthe authorization request message so that the issuer can betterdetermine whether to decline the transaction for not being initiated bythe verified cardholder, or (2) automatically decline the transaction onbehalf of the issuer. Server computing device 275 is also configured totransmit an authorization response message authorizing the transactionif the transaction secure token matches the registration secure tokenand the issuer authorizes the transaction, or declining the transactionif the received secure token does not match the stored secure tokenand/or the issuer does not authorize the transaction.

FIG. 5 is a block diagram of a payment processing system 500 showingdata flow among vehicle computing device 102 (shown in FIG. 2), apayment processor 502, and a merchant processor 504. In the exemplaryembodiment, system 500 may be a payment processing system such as system100 (shown in FIG. 2). In some embodiments, payment processor 502 may beintegral to or in communication with an interchange network, such asinterchange network 28 (shown in FIG. 1). Vehicle computing device 102enables a cardholder to access payment processor 502 and merchantprocessor 504 and electronically transact with payment processor 502and/or merchant processor 504 to purchase items/services associated witha merchant. In the exemplary embodiment, vehicle computing device 102 iscoupled to and/or integral to a vehicle, such as, but not limited to, anautomobile, a truck, a recreational vehicle, a motorcycle and a marinevessel.

At the time the cardholder registers with payment processor 502, thecardholder inputs a biometric sample that is stored at vehicle computingdevice 102 or at payment processor 502. Vehicle computing device 102uses the biometric sample, associated with a biometric identifier 512,along with other data to generate a registration secure token 506 thatgets stored at the payment processor 502. More specifically, vehiclecomputing device 102 is configured to generate registration secure token506 that includes an account identifier 508, a vehicle identifier 510,and a biometric identifier 512. Account identifier 508, vehicleidentifier 510, and biometric identifier 512 are all input to vehiclecomputing device 102 (e.g., by a cardholder such as cardholder 22, shownin FIG. 1) during the registration process. Account identifier 508 isspecific to each cardholder and may include, without limitation, paymentcard information, contact information (e.g., an email address and/or atelephone number), a promotion code, billing information, and/orshipping information. Payment card information may include, for example,a card identifier (e.g., a primary account number (PAN), a tokenizedPAN, a partial account number, and/or a card name), a security code,and/or an expiry date. Shipping information may include, for example, adelivery address and/or delivery instructions. Different vehicles areassigned unique vehicle identifiers 510 to associate the transactions tothe particular vehicle. Regardless of which cardholder and accountidentifiers 508 are used to purchase the good and/or service, thepurchased item is associated with the vehicle via vehicle identifier510. Vehicle identifier 510 may include, without limitation, a vehicleidentification number (VIN) or any other unique identifier. Vehicleidentifier 510 may be preloaded on the vehicle computing device or maybe input by the cardholder. Additionally, biometric identifier 512 maybe associated with and/or include a biometric sample such as, withoutlimitation, a fingerprint image, a voice recording, a retinal image,facial recognition, palm print image, iris recognition, and the like, orhashed biometric data where a hashing function is applied to biometricdata. Biometric identifier 512 is unique to the cardholder and difficultto duplicate and/or forge by an unauthorized user. Biometric identifier512 is associated with account identifier 508 and vehicle identifier 510and facilitates secure authorization of transactions initiated usingvehicle computing device 102. In some embodiments, vehicle computingdevice 102 is able to generate registration secure tokens 506corresponding to more than one cardholder account. For example, avehicle owner may have more than one cardholder account registered withthe system, or more than one cardholder may drive the vehicle, such asin the case of a family using the vehicle.

Registration secure token 506 is unique to the cardholder and is used toauthenticate transactions initiated at vehicle computing device 102.Registration secure token 506 is stored in vehicle computing device 102,and is also transmitted 550 to payment processor 502. Payment processor502 stores registration secure token 506.

Each time the cardholder initiates a transaction from vehicle computingdevice 102, the cardholder inputs a biometric input that gets comparedto the stored biometric sample. If it matches, vehicle computing device102 generates a transaction secure token 514 including the biometricidentifier 512, account identifier 508, and vehicle identifier 510.

Transaction secure token 514 is communicated 552 to merchant processor504. Merchant processor 504 includes a merchant computing device 516. Inthe example embodiment, merchant computing device 516 may be a computingdevice such as user computing device 200 (shown in FIG. 3). Merchantcomputing device 516 is a service-provider device that iscommunicatively coupled to merchant processor 504. Merchant computingdevice 516 facilitates communication 552 of transaction data fromvehicle computing device 102 to payment processor 502. Specifically, amerchant point-of-service (POS) device 520 facilitates conducting apayment transaction and receiving transaction secure token 514, afterthe cardholder initiates the payment transaction, from vehicle computingdevice 102 via a wireless transmission such as near field transmissionor Bluetooth transmission. When merchant processor 504 receivestransaction data including transaction secure token 514, merchantcomputing device 516 generates a payment authorization request message522 including transaction secure token 514. Payment authorizationrequest message 522 is transmitted to payment processor 502,specifically to a payment processor computing device 524, for processingand further transmission to an issuing bank for approval.

Upon receipt of payment authorization request message 522, paymentprocessor computing device 524 authenticates payment authorizationrequest message 522 by determining that transaction secure token 514sent with payment authorization request message 522 matches registrationsecure token 506 corresponding to the cardholder that was created aspart of the registration process. If transaction secure token 514matches registration secure token stored at payment processor computingdevice 524, then payment processor computing device 524 embeds amatching indicator into authorization request message 522. The matchingindicator advises the issuer that transaction secure token 514 matchesregistration secure token 506, and thus, the transaction has beeninitially verified as being initiated by the authorized cardholder. If,however, transaction secure token 514 does not match registration securetoken 506, then payment processor computing device 524 is configured toeither (i) embed a “no match” indicator into authorization requestmessage 522 so that the issuer can decline the transaction for not beingfrom the verified cardholder, or (2) automatically decline thetransaction on behalf of the issuer. Payment processor computing device524 is also configured to transmit to merchant processor 504 anauthorization response message 526 authorizing the transaction, iftransaction secure token 514 matches registration secure token 506 andthe issuer approves the transaction.

Payment processor computing device 524 is used for processing themerchant transactions. In one embodiment, payment processor computingdevice 524 includes an interchange computer associated with aninterchange network. Payment authorization response message 526 isreceived from the issuing bank and transmitted to merchant computingdevice 516 by payment processor computing device 524.

In one embodiment, upon receipt of payment authorization request message522, payment processor computing device 524 authenticates paymentauthorization request message 522. More specifically, payment processorcomputing device 524 determines that transaction secure token 514included in payment authorization request message 522 matchesregistration secure token 506 corresponding to the cardholder. Iftransaction secure token 514 matches registration secure token 506, aconfirmation response message (not shown) indicating that thetransaction is undergoing issuer authorization is sent to merchantcomputing device 516. However, if transaction secure token 514 does notmatch registration secure token 506, a rejection response message (notshown) declining the transaction on behalf of the issuer is sent tomerchant computing device 516.

In some embodiments, payment processor computing device 524 furtherverifies payment authorization request message 522 by applying at leastone verification rule and determining that payment authorization requestmessage 522 is a verified message. For example, payment authorizationrequest message 522 is verified if it is determined that a currentlocation of the cardholder's vehicle as sent by vehicle computing device102 corresponds to a location of merchant POS device 520 provided bymerchant computing device 516. If the vehicle location and the merchantlocation correspond then payment authorization request message 522 isverified. However, if the vehicle location and the merchant location donot correspond then payment authorization request message 522 isrejected. In another example, payment authorization request message 522is verified if it is determined that a current mileage of thecardholder's vehicle as sent by vehicle computing device 102 is greaterthan a previous mileage of the vehicle corresponding to a previoustransaction. If the current mileage of the vehicle is greater than aprevious transaction's mileage then payment authorization request 522 isverified. However, if the current mileage of the vehicle is less than aprevious transaction's mileage then payment authorization request 522 isrejected.

In other embodiments, payment processor computing device 524 may receivecoupons from merchants and merchant computing device 516 with priortransaction history to distribute to the cardholder (specifically, tovehicle computing device 102) and to be used in any future transactionswith the merchant. As such, payment processor computing device 524 alsofacilitates transmitting merchant coupons to the cardholder and vehiclecomputing device 102 for use in future merchant transactions.

FIG. 6 is a flowchart illustrating an exemplary method 600 for using avehicle computing device, such as vehicle computing device 102 (shown inFIG. 2), when performing an electronic transaction in accordance withone embodiment of the present invention. In one embodiment, method 600may be implemented by system 100 (shown in FIG. 2). In the exemplaryembodiment, method 600 relates to the receiving and transmitting ofmessages and information among vehicle computing device 102, merchantcomputing device 516, and payment processor computing device 524 (allshown in FIG. 5). While operations within the method 600 are describedbelow with regard to particular devices and/or systems, method 600 maybe implemented on other such devices and/or systems by one skilled inthe art.

During operation, payment processor computing device 524 receives 602 aregistration (or first) secure token from vehicle computing device 102.The registration secure token corresponds to a cardholder and includesan account identifier, such as account identifier 508, a vehicleidentifier, such as vehicle identifier 510, and a biometric identifier,such as biometric identifier 512 (all shown in FIG. 5). The registrationsecure token is then stored 604 by payment processor computing device524. When the cardholder initiates an electronic transaction with amerchant, payment processor computing device 524 receives 606 a paymentauthorization request message, such as message 522, generated frommerchant computing device 516. The payment authorization request messageincludes a transaction (or second) secure token, such as token 506,received from vehicle computing device 102 by merchant computing device516 when the cardholder inputs the biometric identifier and initiatesthe electronic transaction. The payment authorization request message522 is transmitted from merchant computing device 516 to paymentprocessor computing device 524 for processing and further transmissionto an issuing bank for approval.

Payment processor computing device 524 authenticates 608 the paymentauthorization request message by determining that the transaction securetoken within the payment authorization request message matches thestored registration secure token. If the transaction secure tokenmatches the stored registration secure token, then payment processorcomputing device 524 embeds a matching indicator into the authorizationrequest message advising the issuer that the received secure tokenmatches the stored secure token, and thus, the transaction has beeninitially verified as being initiated by the authorized cardholder. If,however, the transaction secure token included within the paymentauthorization request message does not match the stored secure token atpayment processor computing device 524, then payment processor computingdevice 524 is configured to either (i) embed a “no match” indicator intothe authorization request message so that the issuer can decline thetransaction for not being a verified cardholder transaction, or (ii)automatically decline the transaction on behalf of the issuer. If theauthorization request message is authorized, then payment processorcomputing device 524 generates and transmits 610 a confirmationresponse, such as payment authorization response message 526 (shown inFIG. 5), authorizing the transaction to merchant computing device 516.

In some embodiments, payment processor computing device 524 furtherverifies the payment authorization request message by applying at leastone verification rule and determining that the payment authorizationrequest message is a verified message. While in other embodiments,payment processor computing device 524 may receive coupons frommerchants and merchant computing device 516 distribute to the cardholderand to be used in any future transactions with the merchant. As such,the payment processor computing device 524 also facilitates transmittingmerchant coupons to the cardholder and vehicle computing device 102 foruse in future merchant transactions.

In some embodiments, one or more messages sent between the differentcomputer systems, or a portion thereof, are encrypted by the sendingdevice and decrypted by the receiving device. For example, the paymentauthorization response message may be encrypted by the payment processorcomputing device and decrypted by the merchant computing device. In oneembodiment, the interchange computer system encrypts an account number(e.g., a PAN) and/or secure token using a public key assigned to themerchant, and the merchant computing system decrypts the account numberusing a private key corresponding to the public key. For example, theprivate key and the public key may be assigned to the merchant by theinterchange network for use in signing documents and/or messages, andmay also be used for encrypting messages transmitted between themerchant and the interchange network.

While the invention has been described in terms of various specificembodiments, those skilled in the art recognize that the invention canbe practiced with modification within the spirit and scope of theclaims.

Exemplary embodiments of methods, systems, and computer-readable storagemedia for use in implementing an electronic transaction processingsystem are described above in detail. The methods, systems, and storagemedia are not limited to the specific embodiments described herein but,rather, operations of the methods and/or components of the system may beutilized independently and separately from other operations and/orcomponents described herein. Further, the described operations and/orcomponents may also be defined in, or used in combination with, othersystems, methods, and/or storage media, and are not limited to practicewith only the methods, systems, and storage media as described herein.

Computer programs (also known as programs, software, softwareapplications, “apps”, or code) include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” and “computer-readable medium” refer to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor, including amachine-readable medium that receives machine instructions as amachine-readable signal. The “machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

As used herein, the terms “card,” “transaction card,” “financialtransaction card,” and “payment card” refer to any suitable transactioncard, such as a credit card, a debit card, a prepaid card, a chargecard, a membership card, a promotional card, a frequent flyer card, anidentification card, a gift card, and/or any other device that may holdpayment account information, such as vehicle computing devices, mobilephones, Smartphones, personal digital assistants (PDAs), key fobs,and/or computers. Each type of transaction card can be used as a methodof payment for performing a transaction. In addition, consumer cardaccount behavior can include, but is not limited to, purchases,management activities (e.g., balance checking), bill payments,achievement of targets (meeting account balance goals, paying bills ontime), and/or product registrations (e.g., mobile applicationdownloads). The term “transaction card” or “payment card” can also referto a bank account associated with a user or cardholder that is issued byan issuing bank whether or not a physical card is provided to thecardholder by the issuing bank.

For example, one or more computer-readable storage media may includecomputer-executable instructions embodied thereon for regulatingaccount-on-file information. In this example, the computing device mayinclude a memory device and a processor in communication with the memorydevice, and when executed by said processor, the computer-executableinstructions may cause the processor to perform a method, such as themethods described and illustrated in the examples of FIG. 6.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.”

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

Although the present invention is described in connection with anexemplary electronic transaction processing system environment,embodiments of the invention are operational with numerous other generalpurpose or special purpose electronic transaction processing systemenvironments or configurations. The electronic transaction processingsystem environment is not intended to suggest any limitation as to thescope of use or functionality of any aspect of the invention. Moreover,the electronic transaction processing system environment should not beinterpreted as having any dependency or requirement relating to any oneor combination of components illustrated in the exemplary operatingenvironment. Examples of well-known electronic transaction processingsystems, environments, and/or configurations that may be suitable foruse with the embodiments described herein include, but are not limitedto, embedded computing devices, personal computers, server computers,hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, mobile telephones, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

The order of execution or performance of the operations in theembodiments illustrated and described herein is not essential, unlessotherwise specified. That is, the operations may be performed in anyorder, unless otherwise specified, and embodiments may includeadditional or fewer operations than those disclosed herein. For example,it is contemplated that executing or performing a particular operationbefore, contemporaneously with, or after another operation is within thescope of the described embodiments.

Although specific features of various embodiments of the invention maybe shown in some drawings and not in others, this is for convenienceonly. In accordance with the principles of the invention, any feature ofa drawing may be referenced and/or claimed in combination with anyfeature of any other drawing.

This written description uses examples to disclose the invention,including the best mode, and also to enable any person skilled in theart to practice the invention, including making and using any devices orsystems and performing any incorporated processes. The patentable scopeof the invention is defined by the claims, and may include otherexamples that occur to those skilled in the art. These other examplesare intended to be within the scope of the claims if they havestructural elements that do not differ from the literal language of theclaims, or if they include equivalent structural elements withinsubstantial differences from the literal language of the claims.

What is claimed is:
 1. A payment processor computing device forperforming an electronic transaction initiated by a vehicle including avehicle computing device, said payment processor computing devicecomprising one or more processors in communication with one or morememory devices, said payment processor computing device communicativelycoupled to the vehicle computing device and to at least one merchantpoint-of-sale (POS) device, said payment processor computing deviceconfigured to: receive a registration secure token from a vehiclecomputing device, the registration secure token being unique to acombination of a cardholder and the vehicle associated with thecardholder and created during a registration process for initiatingfuture electronic transactions, the vehicle computing device coupled tothe vehicle, the registration secure token including: a tokenizedaccount identifier, the cardholder having an account associated with theaccount identifier for use in processing electronic transactions; avehicle identifier unique to the vehicle associated with the cardholder;and a biometric identifier associated with the cardholder, the biometricidentifier generated by the vehicle computing device in response toreceiving a first biometric input from a biometric input deviceconnected to the vehicle computing device, wherein the first biometricinput is stored in a memory device of the vehicle computing device;store the registration secure token in the one or more memory devices;receive an authorization request message associated with a paymenttransaction initiated by the cardholder using the vehicle computingdevice in communication with a first merchant POS device, theauthorization request message sent by the vehicle computing device tosaid payment processor computing device via the first merchant POSdevice physically proximate to the vehicle computing device, theauthorization request message including transaction data associated withthe payment transaction and a transaction secure token, wherein thetransaction secure token includes the tokenized account identifier, thevehicle identifier of the vehicle, and the biometric identifier, andwherein the transaction secure token is generated by the vehiclecomputing device in response to the vehicle computing device receiving asecond biometric input from the biometric input device, the secondbiometric input substantially matching the first biometric input storedin the memory of the vehicle computing device; authenticate theauthorization request message by matching the transaction secure tokento the registration secure token, the matching including (i) matching afirst portion of the transaction secure token representing the tokenizedaccount identifier and a second portion of the transaction secure tokenrepresenting the vehicle identifier to a first portion of theregistration secure token representing the tokenized account identifierand a second portion of the registration secure token representing thevehicle identifier to verify the payment account being used to initiatethe payment transaction via the vehicle computing device is associatedwith the vehicle associated with the vehicle identifier and that thevehicle associated with the vehicle identifier is in proximity to thefirst merchant POS device at the time the payment transaction isinitiated, and (ii) matching a third portion of the transaction securetoken representing the biometric identifier to a third portion of theregistration secure token representing the biometric identifier toverify a registered cardholder is initiating the payment transaction;embed a matching indicator within the authorization request message, thematching indicator representing successful verification of the paymenttransaction based upon successful matching of the transaction securetoken with the registration secure token; and transmit the authorizationrequest message with the embedded matching indicator to an issuer of theaccount for further processing, wherein, upon detection of the embeddedmatching indicator by the issuer, the embedded matching indicator isconfigured to indicate initial verification of the payment transactionhas been performed by the payment processing computer device and causeexpedited issuer authentication and authorization of the paymenttransaction.
 2. The payment processor computing device of claim 1,wherein said payment processor computing device is further configured toreceive the registration secure token in response to the cardholderinputting the account identifier and the vehicle identifier during theregistration process.
 3. The payment processor computing device of claim1, wherein the first biometric input includes at least one of afingerprint image, a voice recording, and a retinal image of thecardholder.
 4. The payment processor computing device of claim 1,wherein said payment processor computing device is further configured toverify the authorization request message by applying at least oneverification rule and determining that the authorization request messageis a verified message.
 5. The payment processor computing device ofclaim 4, wherein the at least one verification rule for determining thatthe authorization request message is verified includes at least one of:(i) determining that a current location of the vehicle corresponds to alocation of the first merchant POS device based on a vehicle locationreceived from the first merchant POS device in the authorization requestmessage; and (ii) determining that a current mileage of the vehicle isgreater than a previous mileage of the vehicle when performing aprevious transaction based on a vehicle mileage received from the firstmerchant POS device in the authorization request message.
 6. The paymentprocessor computing device of claim 1, wherein said payment processorcomputing device is further configured to transmit at least one couponto the vehicle computing device based on prior transactions.
 7. Thepayment processor computing device of claim 1, wherein said paymentprocessor computing device is further configured to receive a pluralityof registration secure tokens from the vehicle computing device, each ofthe plurality of registration secure tokens unique to a respectivecombination of another cardholder of a plurality of cardholders linkedto the vehicle and the vehicle.
 8. The payment processor computingdevice of claim 1, wherein the vehicle identifier is a vehicleidentification number (VIN) associated with the vehicle by a vehiclemanufacturer.
 9. The payment processor computing device of claim 1, saidpayment processor computing device further configured to: determine thatthe transaction secure token does not match the registration securetoken; embed a no-match indicator within the authorization requestmessage; and transmit the authorization request message with theembedded no-match indicator to an issuer of the account for furtherprocessing, wherein, upon detection of the embedded no-match indicatorby the issuer, the embedded no-match indicator is configured to indicateinitial verification of the payment transaction performed by the paymentprocessing computer device was unsuccessful and cause the issuer to (i)initiate one or more additional authentication procedures, or (ii)decline the payment transaction.
 10. The payment processor computingdevice of claim 1, said payment processor computing device furtherconfigured to: determine that the transaction secure token does notmatch the registration secure token; generate, on behalf of the issuer,an authorization response message including a decline message and ano-match indicator; and transmit the authorization response messageincluding the embedded no-match indicator to the merchant computingdevice to terminate the electronic transaction.
 11. Acomputer-implemented method for performing an electronic transactioninitiated by a vehicle including a vehicle computing device coupled tothe vehicle, said method implemented using a payment processor computingdevice communicatively coupled to the vehicle computing device and to atleast one merchant point-of-sale (POS) device, the vehicle computingdevice and the payment processor computing device each having at leastone processor and one or more memory devices, said method comprising:generating, by the vehicle computing device, a biometric identifierassociated with a cardholder in response to receiving a first biometricinput from a biometric input device connected to the vehicle computingdevice, wherein the first biometric input is stored in the one or morememory devices of the vehicle computing device; receiving, by thepayment processor computing device, a registration secure token from thevehicle computing device, the registration secure token being unique toa combination of the cardholder the vehicle associated with thecardholder and created during a registration process for initiatingfuture electronic transactions, the registration secure token includinga tokenized account identifier, a vehicle identifier unique to thevehicle associated with the cardholder, and the biometric identifier,the cardholder having an account associated with the account identifierfor use in processing electronic transactions, and the cardholder beingassociated with the biometric identifier; storing, by the paymentprocessor computing device, the registration secure token in the one ormore memory devices; receiving, by the payment processor computingdevice, an authorization request message associated with a paymenttransaction initiated by the cardholder using the vehicle computingdevice in communication with first merchant POS device, theauthorization request message sent by the vehicle computing device tothe payment processor computing device via the first merchant POS devicephysically proximate to the vehicle computing device, the authorizationrequest message including transaction data associated with the paymenttransaction and a transaction secure token that includes the tokenizedaccount identifier, the vehicle identifier of the vehicle, and thebiometric identifier, wherein the transaction secure token is generatedby the vehicle computing device in response to the vehicle computingdevice receiving a second biometric input from the biometric inputdevice, the second biometric input substantially matching the firstbiometric input stored in the one or more memory devices of the vehiclecomputing device; authenticating, by the payment processor computingdevice, the authorization request message by matching the transactionsecure token to the registration secure token, said matching including(i) matching a first portion of the transaction secure tokenrepresenting the tokenized account identifier and a second portion ofthe transaction secure token representing the vehicle identifier to afirst portion of the registration secure token representing thetokenized account identifier and a second portion of the registrationsecure token representing the vehicle identifier to verify the paymentaccount being used to initiate the payment transaction via the vehiclecomputing device is associated with the vehicle associated with thevehicle identifier and that the vehicle associated with the vehicleidentifier is in proximity to the first merchant POS device at the timethe payment transaction is initiated, and (ii) matching a third portionof the transaction secure token representing the biometric identifier toa third portion of the registration secure token representing thebiometric identifier to verify a registered cardholder is initiating thepayment transaction; embedding a matching indicator within theauthorization request message, the matching indicator representingsuccessful verification of the payment transaction based upon successfulmatching of the transaction secure token with the registration securetoken; and transmitting the authorization request message with theembedded matching indicator to an issuer of the account for furtherprocessing, wherein, upon detection of the embedded matching indicatorby the issuer, the embedded matching indicator is configured to indicateinitial verification of the payment transaction has been performed bythe payment processing computer device and cause expedited issuerauthentication and authorization of the payment transaction.
 12. Themethod of claim 11, wherein receiving a registration secure tokenfurther comprises receiving the registration secure token in response tothe cardholder inputting the account identifier and the vehicleidentifier during the registration process.
 13. The method of claim 11,wherein the first biometric input includes at least one of a fingerprintimage, a voice recording, and a retinal image of the cardholder.
 14. Themethod of claim 11 further comprising verifying the authorizationrequest message, by the payment processor computing device, by applyingat least one verification rule and determining that the authorizationrequest message is a verified message.
 15. The method of claim 14,wherein the at least one verification rule for determining that theauthorization request message is verified includes at least one of: (i)determining that a current location of the vehicle corresponds to alocation of first merchant POS device based on a vehicle locationreceived from the first merchant POS device in the authorization requestmessage; and (ii) determining that a current mileage of the vehicle isgreater than a previous mileage of the vehicle corresponding to aprevious transaction based on a vehicle mileage received from the firstmerchant POS device in the authorization request message.
 16. The methodof claim 11 further comprising transmitting at least one coupon from thepayment processor computing device to the vehicle computing device basedon prior transactions.
 17. The method of claim 11 further comprisingreceiving at the payment processor computing device a plurality ofregistration secure tokens from the vehicle computing device, each ofthe plurality of registration secure tokens unique to a respectivecombination of another cardholder of a plurality of cardholders linkedto the vehicle and the vehicle.
 18. A non-transitory computer readablemedium that includes computer executable instructions for performing anelectronic transaction initiated by a vehicle including a vehiclecomputing device using a payment processor computing device incommunication with a payment network and the vehicle computing deviceand to at least one merchant point-of-sale (POS) device, wherein whenexecuted by the payment processor computing device, the computerexecutable instructions cause the payment processor computing device to:receive a registration secure token from a vehicle computing device, theregistration secure token being unique to a combination of a cardholderand the vehicle associated with the cardholder and created during aregistration process for initiating future electronic transactions, thevehicle computing device coupled to the vehicle, the registration securetoken including: a tokenized account identifier, the cardholder havingan account associated with the account identifier for use in processingelectronic transactions; a vehicle identifier unique to the vehicleassociated with the cardholder; and a biometric identifier associatedwith the cardholder, the biometric identifier generated by the vehiclecomputing device in response to receiving a first biometric input from abiometric input device connected to the vehicle computing device,wherein the first biometric input is stored in a memory device of thevehicle computing device; store the registration secure token in the oneor more memory devices; receive an authorization request messageassociated with a payment transaction initiated by the cardholder usingthe vehicle computing device in communication with a first merchant POSdevice, the authorization request message sent by the vehicle computingdevice to said payment processor computing device via the first merchantPOS device physically proximate to the vehicle computing device, theauthorization request message including transaction data associated withthe payment transaction and a transaction secure token, wherein thetransaction secure token includes the tokenized account identifier, thevehicle identifier of the vehicle, and the biometric identifier, andwherein the transaction secure token is generated by the vehiclecomputing device in response to the vehicle computing device receiving asecond biometric input from the biometric input device, the secondbiometric input substantially matching the first biometric input storedin the memory of the vehicle computing device; authenticate theauthorization request message by matching the transaction secure tokento the registration secure token, the matching including (i) matching afirst portion of the transaction secure token representing the tokenizedaccount identifier and a second portion of the transaction secure tokenrepresenting the vehicle identifier to a first portion of theregistration secure token representing the tokenized account identifierand a second portion of the registration secure token representing thevehicle identifier to verify the payment account being used to initiatethe payment transaction via the vehicle computing device is associatedwith the vehicle associated with the vehicle identifier and that thevehicle associated with the vehicle identifier is in proximity to thefirst merchant POS device at the time the payment transaction isinitiated, and (ii) matching a third portion of the transaction securetoken representing the biometric identifier to a third portion of theregistration secure token representing the biometric identifier toverify a registered cardholder is initiating the payment transaction;embed a matching indicator within the authorization request message, thematching indicator representing successful verification of the paymenttransaction based upon successful matching of the transaction securetoken with the registration secure token; and transmit the authorizationrequest message with the embedded matching indicator to an issuer of theaccount for further processing wherein, upon detection of the embeddedmatching indicator by the issuer, the embedded matching indicator isconfigured to indicate initial verification of the payment transactionhas been performed by the payment processing computer device and causeexpedited issuer authentication and authorization of the paymenttransaction.
 19. The non-transitory computer readable medium of claim18, wherein the computer executable instructions cause the paymentprocessor computing device to receive the registration secure token inresponse to the cardholder inputting the account identifier and thevehicle identifier during the registration process.
 20. Thenon-transitory computer readable medium of claim 18, wherein thecomputer executable instructions cause the payment processor computingdevice to verify the authorization request message by applying at leastone verification rule and determining that the authorization requestmessage is a verified message.
 21. The non-transitory computer readablemedium of claim 18, wherein the computer executable instructions causethe payment processor computing device to transmit at least one couponto the vehicle computing device based on prior transactions.